Skip to content

Conversation

@gabriel-farache
Copy link
Contributor

@gabriel-farache gabriel-farache commented Jun 6, 2025

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@gabriel-farache gabriel-farache requested a review from a team as a code owner June 6, 2025 13:34
@gabriel-farache
Copy link
Contributor Author

@ricardozanini the follow up of #1126

@gabriel-farache gabriel-farache force-pushed the fix/oauth2_provider_credentialProvider_bis branch 2 times, most recently from 52ff5d5 to bb77674 Compare June 6, 2025 13:39
@ricardozanini
Copy link
Member

These changes are fine, we just have to change the constructor as I mentioned in #1126

@gabriel-farache
Copy link
Contributor Author

Constructors removed in #1176

Copy link
Contributor

@gmunozfe gmunozfe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, just resolve the conflicts before merge, well done @gabriel-farache !

@gmunozfe gmunozfe self-requested a review June 9, 2025 07:57
@gabriel-farache gabriel-farache force-pushed the fix/oauth2_provider_credentialProvider_bis branch from bb77674 to 006df17 Compare June 10, 2025 07:27
Copy link
Contributor

@gmunozfe gmunozfe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well done @gabriel-farache !

@ricardozanini ricardozanini merged commit 75994db into quarkiverse:main Jun 10, 2025
11 checks passed
ricardozanini pushed a commit to ricardozanini/quarkus-openapi-generator that referenced this pull request Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants